-
Notifications
You must be signed in to change notification settings - Fork 83
New Operations manual front page #2183
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
This PR includes documentation updates Updated pages: |
NataliaIvakina
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it looks very good and promising. I left some comments and will help with the list for COSI.
modules/ROOT/pages/index.adoc
Outdated
| == Tutorials & How-to guides | ||
|
|
||
| [.icon] | ||
| image:ga-home.svg[] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can't see your screenshot, unfortunately. Can you send it to me over Slack so I understand what you mean?
|
Hey, @lidiazuin, thanks a lot for your effort. I think we are going in a good direction. On Friday, David Pond and I went over the Miro board, and we agreed that it makes sense only if we put the right content there. So, this is what we agreed on, and this is what I tried to also show on the board. What we need is:
|
We've just updated the license page with additional information. Why do we want this manual to not link to our own license page (which includes a link to the full CC license text)? |
Co-authored-by: NataliaIvakina <[email protected]>
|
|
Hi @renetapopova thanks for your input!
So, the current layout is set to have only three cards in one line, like in neo4j.com/docs. If you want four lists, the option is to use the widget that we have now with the four lists (Neo4j admin commands, Cypher admin commands, etc). I will update the PR so you can see how it would look without the COSI option.
It was a legal demand that we use this kind of link now, all manuals need to refer to this page because the whole documentation now needs to be under these same notices and licenses. Please refer to David for more details, we worked together to come up with this. |
We have updated the Miro board to include three cards. Below them, we can add the Neo4j Admin command in four columns. |
renetapopova
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some comments on the intro sentences.
renetapopova
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's starting to look very nice. I added some more comments.
modules/ROOT/pages/index.adoc
Outdated
| [.display.cards] | ||
|
|
||
| For all information on *upgrading and migrating Neo4j*, see the link:{neo4j-docs-base-uri}/upgrade-migration-guide/current/[Neo4j Upgrade and Migration Guide]. | ||
| == Install, deploy and operate Neo4j in a self-managed environment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks much better now.
However, I still think that having an intro sentence looks better than starting with "For more information...". If we have to remove something, then let's remove these two sentences:
"For information on upgrading and migrating Neo4j, see the link:https://neo4j.com/docs/upgrade-migration-guide/[Neo4j Upgrade and Migration] documentation.
For link:https://neo4j.com/aura/[Aura], the Neo4j fully managed cloud service, see the link:https://neo4j.com/docs/aura[Neo4j Aura] documentation."
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You mean keeping only the info about the current Neo4j version then?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, I mean removing this heading: Install, deploy and operate Neo4j in a self-managed environment and having a sentence instead like I already suggested:
| == Install, deploy and operate Neo4j in a self-managed environment | |
| Neo4j Operations includes all the operational details and instructions for installing, deploying, and operating Neo4j in a self-managed environment. | |
| The latest version of Neo4j is *{neo4j-version-exact}*. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can add the introductory sentence, but the layout has this formatting and we should stick to a more standardizing approach.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But who created this layout? Can't we amend it to suit our needs? Or we can have slightly different layouts for different needs/manuals?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sebastian from the design team created this, DocOps executes it. We can make amends when necessary for a functional reason, which I believe it's not the case here. We need to make sure we follow a standard and create consistency across all docsets.
Co-authored-by: Reneta Popova <[email protected]>
renetapopova
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some more comments
modules/ROOT/pages/index.adoc
Outdated
| [.display.cards] | ||
|
|
||
| For all information on *upgrading and migrating Neo4j*, see the link:{neo4j-docs-base-uri}/upgrade-migration-guide/current/[Neo4j Upgrade and Migration Guide]. | ||
| == Install, deploy and operate Neo4j in a self-managed environment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, I mean removing this heading: Install, deploy and operate Neo4j in a self-managed environment and having a sentence instead like I already suggested:
| == Install, deploy and operate Neo4j in a self-managed environment | |
| Neo4j Operations includes all the operational details and instructions for installing, deploying, and operating Neo4j in a self-managed environment. | |
| The latest version of Neo4j is *{neo4j-version-exact}*. |
|
This PR includes documentation updates Updated pages: |
| Documentation license: <<license, Creative Commons 4.0>> | ||
| endif::[] | ||
| [.link] | ||
| link:https://neo4j.com/docs/license[Licenses and disclaimers] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey, @davidoliverSP2, this is what we've been talking about. Could you be able to check with legal if we need the licenses on each manual at all, and, if we need them, whether we could link to the licenses that apply to this manual directly or at least to a specific docs' page where only this license is explained? If I am a user, I would rather read the whole license instead of a company's summary of it, but if the legal think that this is needed, that's fine with me. I just think it should be easy for the user to see what licenses we comply with.
|
Closing this PR in favor of the upcoming re-architecture work. |
|
Thanks for the documentation updates. The preview documentation has now been torn down - reopening this PR will republish it. |
Proposition of a new front page for the operations manual including recommended resources and most visited pages.